$ @vmsinstal vms040


        VAX/VMS Software Product Installation Procedure


It is 1-SEP-1984 at 10:29.
Enter a question mark (?) at any time for help.

* Are you satisfied with the backup of your system disk [YES]? yes
* Where will the distribution volumes be mounted: msa0:

Please mount the first volume of the set on MSA0:.
* Are you ready? yes

%MOUNT-I-MOUNTED, VMS040 mounted on _MSA0:

The following products will be installed:

  VMS    V4.0


        Beginning installation of VMS V4.0 at 10:30

%VMSINSTAL-I-RESTORE, Restoring product saveset A...

                        VAX/VMS V4.0 Upgrade Procedure

This procedure will convert a VAX/VMS V3.4, V3.5, V3.6, or V3.7 system disk into
a VAX/VMS V4.0 system disk.  To accomplish this, the system must  be rebooted
several times.  The upgrade will continue automatically after each reboot via a
specially created system startup command procedure. 



                               IMPORTANT

The distribution kit may not be placed in any directory except [000000].  If you
have moved the required savesets to a different directory please exit from the
upgrade and move them to a [000000] directory. 

The pagefile, swapfile, dump file, and user authorization file will all be
purged to one version.  All accounting and operator logs will be deleted.
Everything in [SYSERR] will also be deleted. All *.JNL files in the system
directory tree will be deleted. 

If you wish to preserve any of these files, please exit from the upgrade and
move them to a user directory. 

RESTAR.CMD must match the memory interleaving of your system configuration.
If this is incorrect and there is a power failure, the upgrade will not
recover correctly.  If you are unsure of the setting of RESTAR.CMD, contact
your Field Service representative.

AUTOGEN may attempt to re-size your primary pagefile or swapfile. You can
control this via entries in the parameter file SYS$SYSTEM:MODPARAMS.DAT. See
the Guide to VAX/VMS System Management and Daily Operations for detailed
information. 


Do you want to continue? (Y/N): y

                Upgrade Phase 1          1-SEP-1984 10:30:11.44

Now we will ask you for new passwords for the following accounts:
        SYSTEM, SYSTEST, FIELD


Enter new password for account SYSTEM: 
Re-enter the password for account SYSTEM for verification: 

user record(s) updated

Enter new password for account SYSTEST: 
Re-enter the password for account SYSTEST for verification: 

user record(s) updated

Enter new password for account FIELD: 
Re-enter the password for account FIELD for verification: 

user record(s) updated

Turning off disk quotas on system disk.
%DISKQ-E-DACTERR, failed to disable quota file
%SYSTEM-E-QFNOTACT, disk quota file is not active
%SYSTEM-W-NONEXPR, nonexistent process
%SYSTEM-W-NONEXPR, nonexistent process
%SYSTEM-W-NONEXPR, nonexistent process

Now a new site-specific floppy must be created to allow
reboot of a kernel VAX/VMS V4.0 system.

Your old console floppy should be in drive CS1:.
Your old console will not be modified during the upgrade.

Is the old console floppy, CS1:, ready to be mounted? (Y/N): y

%MOUNT-I-MOUNTED,              mounted on _CSA1:

The old console floppy will be copied to a scratch
directory now.  Afterwards you will be asked to insert
a scratch floppy.  This copy takes about 5 minutes.

If you have not done so previously, you must now set DEFBOO.CMD
to boot the system from your current system disk.

Do you need to set up your DEFBOO.CMD? (Y/N): n

Modifying DEFBOO.CMD to boot V4 from [SYSF.SYSEXE].

Put a scratch console floppy into drive CS1:.
This will be initialized now to verify that the media is
usable and written just before the system is rebooted, in
order to boot from the V4.0 kernel.

DO NOT put your normal console media back in the console drive
during the remainder of the upgrade procedure.


Is a scratch console floppy, now in CS1:? (Y/N): 
Simulation stopped, PC: 80007B06 (BRB 80007B06)

$! Insert scratch console floppy
sim> att rx console_780_VMS4.0.rx1
sim> c


Is a scratch console floppy, now in CS1:? (Y/N): y

%MOUNT-I-MOUNTED,              mounted on _CSA1:

Do you want to run BAD on the new console floppy [Y]: 

Running BAD on new console floppy.
BAD -- CS1: TOTAL BAD BLOCKS= 0.

Initializing the scratch console floppy.

The upgrade procedure will continue automatically for the next two hours.
It reboots automatically with no operator intervention needed from here on. 

        Start directory clean up.
This section takes a variable amount of time
depending on the number of files on the disk.
Directory cleanup complete.

Removing installed images.

Now removing all VAX/VMS V3.7 files not needed
to complete the upgrade.

Purging old accounting data files, operator logs, and [SYSERR].
%PURGE-I-NOFILPURG, no files purged for DBA2:[SYS0.SYSMGR]ACCOUNTNG.DAT;
%PURGE-I-NOFILPURG, no files purged for DBA2:[SYS0.SYSERR]*.*;

Deleting [SYS0...]*.JNL;*

Now creating the new directory tree in [SYSF...] and deleting
all files in [SYS0...] not needed to boot the system.
Now working on files in [SYS0.SYSEXE].
Now working on files in [SYS0.SYSMSG].
Now working on files in [SYS0.SYSEXE].
Now working on files in [SYS0.SYSERR].
Now working on files in [SYS0.SYSEXE].
Now working on files in [SYS0.SYSLIB].
Now working on files in [SYS0.SYSMSG].
Now working on files in [SYS0.SYSMGR].
Now working on files in [SYS0.SYSUPD].
Now working on files in [SYS0.SYSEXE].
Now working on files in [SYS0.SYSHLP].
Now working on files in [SYS0.SYSLIB].
Now working on files in [SYS0.SYSHLP.EXAMPLES].
Now working on files in [SYS0.SYSTEST].
Now working on files in [SYS0.SYSUPD].
Now working on files in [SYS0.SYSLIB].
Now working on files in [SYS0.SYSEXE].
Now working on files in [SYS0.SYSMSG].
Now working on files in [SYS0.SYSMGR].
Now working on files in [SYS0.SYSHLP].
Now working on files in [SYS0.SYSCBI].
Now working on files in [SYS0.SYSTEST].

Now copying over the V4.0 required saveset.
%BACKUP-I-STARTVERIFY, starting verification pass

Purging pagefile, swapfile, dump file, and authorization
files back to one version.
(Please ignore possible file not found messages.)
%PURGE-I-NOFILPURG, no files purged for DBA2:[SYS0.SYSEXE]PAGEFILE.SYS;
%PURGE-I-NOFILPURG, no files purged for DBA2:[SYS0.SYSEXE]SYSDUMP.DMP;
%PURGE-I-NOFILPURG, no files purged for DBA2:[SYS0.SYSEXE]SWAPFILE.SYS;
%PURGE-I-NOFILPURG, no files purged for DBA2:[SYS0.SYSEXE]SYSUAF.DAT;

Entering old page, swap, dump,and authorization files in new directory tree.

Invoke V4 AUTOGEN to save current SYSGEN parameters.

%AUTOGEN-I-BEGIN, SAVPARAMS phase is beginning.
%AUTOGEN-I-NEWFILE, New versions of SYS$SYSTEM:OLDSITE*.DAT have been created.
        You may wish to purge these files.
%AUTOGEN-I-END, SAVPARAMS phase has succesfully completed.

Setting the startup command file for the next phase of the upgrade.

Copying console files to new console floppy.

Writing a boot block on the console media.

System shutting down to boot a kernel V4.0 system.
(Please ignore any error messages during the SHUTDOWN procedure)

Leave the newly created site-specific console floppy
in the console drive for the remainder of the upgrade procedure.

The upgrade procedure will continue automatically after the
reboot.  If for any reason you should have to restart
the upgrade procedure by rebooting by hand, from now on
type only:

                B

The distribution kit must remain on MSA0: and the system disk
must remain on DBA2: in order to proceed to the next phase
of the upgrade.

The sysgen parameters are set to boot any system. Do not
change them during the reboot or the upgrade may fail
to execute properly!

On occasion, this shutdown fails to complete. If the system fails
to shut down within 5 minutes, enter CTRL/P, H, and reboot
as described above to continue the upgrade procedure.


If, for some reason, the kernel V4 system should fail to boot,
you can boot into SYSBOOT by entering

                @UPGGEN.CMD


        System shutdown command procedure.

  Login quotas - Interactive limit=0, Current interactive value=1
        Non-operator logins are disabled.

_OPA0:,SYSTEM       10:35:22.96
Batch and device queues have been stopped.

_OPA0:,SYSTEM       10:35:23.05
System shutdown in 0 minutes; up later.  Logins are disabled; please log out.
Reboot during upgrade procedure
        Stop all user processes.
        Remove installed images.
        Dismount all mounted volumes.
%SYSTEM-W-NONEXPR, nonexistent process
Reboot requested, PC: 800039EC (HALT)
sim> b/r5:F0000000 rp2
Unknown command
sim> sh rp
RP, Massbus adapter 0, 3 units
  RP0, 87MW, attached to RP0-035.dsk, write enabled, RP06
  RP1, 87MW, attached to rp3-040.dsk, write enabled, RP06
  RP2, 87MW, attached to VMS037-RP06.dsk, write enabled, RP06

$! Boot from SYSF (R5:F0000000)
sim> boot rp2/r5:F0000000
Loading boot code from vmb.exe

  
   VAX/VMS Version V4.0 15-SEP-1984 22:29
  

Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> exit
Goodbye
